home *** CD-ROM | disk | FTP | other *** search
- A new Request for Comments is now available in online RFC libraries.
-
-
- RFC 1455:
-
- Title: Physical Link Security Type of Service
- Author: D. Eastlake, III
- Mailbox: dee@ranger.enet.dec.com
- Pages: 6
- Characters: 12,391
- Updates/Obsoletes: none
-
-
- This RFC documents an experimental protocol providing a Type of
- Service (TOS) to request maximum physical link security. This is an
- addition to the types of service enumerated in RFC 1349: Type of
- Service in the Internet Protocol Suite. The new TOS requests the
- network to provide what protection it can against surreptitious
- observation by outside agents of traffic so labeled. The purpose is
- protection against traffic analysis and as an additional possible
- level of data confidentiality. This TOS is consistent with all other
- defined types of service for IP version 4 in that it is based on link
- level characteristics and will not provide any particular guaranteed
- level of service.
-
- This memo defines an Experimental Protocol for the Internet
- community. Discussion and suggestions for improvement are requested.
- Please refer to the current edition of the "IAB Official Protocol
- Standards" for the standardization state and status of this protocol.
- Distribution of this memo is unlimited.
-
- This announcement is sent to the IETF list and the RFC-DIST list.
- Requests to be added to or deleted from the IETF distribution list
- should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added
- to or deleted from the RFC-DIST distribution list should be sent to
- RFC-REQUEST@NIC.DDN.MIL.
-
- Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
- an EMAIL message to "rfc-info@ISI.EDU" with the message body
- "help: ways_to_get_rfcs". For example:
-
- To: rfc-info@ISI.EDU
- Subject: getting rfcs
-
- help: ways_to_get_rfcs
-
- Requests for special distribution should be addressed to either the
- author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
- specifically noted otherwise on the RFC itself, all RFCs are for
- unlimited distribution.
-
- Submissions for Requests for Comments should be sent to
- RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
- Authors", for further information.
-
-
- Joyce K. Reynolds
- USC/Information Sciences Institute
-